-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new locking modes to file handle primitives #151
Open
nathanmemmott
wants to merge
4
commits into
whatwg:main
Choose a base branch
from
nathanmemmott:new_sah_and_wfs_lock_modes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add new locking modes to file handle primitives #151
nathanmemmott
wants to merge
4
commits into
whatwg:main
from
nathanmemmott:new_sah_and_wfs_lock_modes
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a-sully
reviewed
Nov 14, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lots of nits, but the overall shape of this change LGTM
nathanmemmott
force-pushed
the
new_sah_and_wfs_lock_modes
branch
from
November 17, 2023 01:17
bc3475c
to
0eb043a
Compare
5 tasks
a-sully
reviewed
Nov 17, 2023
nathanmemmott
force-pushed
the
new_sah_and_wfs_lock_modes
branch
2 times, most recently
from
November 18, 2023 00:09
dc89f60
to
3f084f0
Compare
a-sully
reviewed
Nov 20, 2023
nathanmemmott
force-pushed
the
new_sah_and_wfs_lock_modes
branch
from
November 21, 2023 00:11
3f084f0
to
9475e66
Compare
a-sully
approved these changes
Nov 21, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but it would be nice to get eyes on this from another implementer before merging
nathanmemmott
force-pushed
the
new_sah_and_wfs_lock_modes
branch
from
November 21, 2023 23:28
9475e66
to
e9ba03b
Compare
Adds new locking modes for sync access handles and writable file streams. Updates "file entry/take a lock" and "file entry/lock/release" to support these new modes.
nathanmemmott
force-pushed
the
new_sah_and_wfs_lock_modes
branch
from
December 20, 2023 22:18
e9ba03b
to
564df68
Compare
This was referenced Aug 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add new locking modes to file handle primitives
Writable file streams and sync access handles can now be created with an optional "mode" parameter.
For sync access handles, "mode" can be "readwrite", "readonly", or "readwrite-unsafe". "readwrite" is the current behavior and the default if "mode" is not specified. Only one sync access handle can be open on a file handle in this mode. The two new modes, "readonly" and "readwrite-unsafe", are shared modes which are added to support multiple readers and writers.
For writable file streams, "mode" can be "exclusive" or "siloed". "siloed" is the current behavior and the default if "mode" is not specified. This mode allows multiple writers to clobber each other. The new "exclusive" mode is added to prevent this clobbering.
For a more detailed explanation, see Multiple Readers and Writers explainer: https://github.com/whatwg/fs/blob/main/proposals/MultipleReadersWriters.md.
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff